Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to React Router 6 #3423

Merged
merged 1 commit into from
May 20, 2024
Merged

Conversation

AlanGreene
Copy link
Member

Changes

#2452

Follow the remaining steps in the migration guide to replace the compat layer with actual use of React Router 6 directly. This includes:

  • move Route children into the element prop
  • refactor use of the Link's component prop to the new approach
  • update tests to avoid relying on history
  • and more

While this does update us to React Router 6 there is still more to be done to take advantage of the new features, such as the handle prop on Routes to avoid the need for our custom NamespacedRoute component etc. This will be tackled in the near future and will dramatically simplify the code, allowing for a more uniform approach to handling Kube resources without the current overhead of custom containers per kind etc.

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Follow the remaining steps in the migration guide to replace the
compat layer with actual use of React Router 6 directly. This includes:
- move `Route` children into the `element` prop
- refactor use of the `Link`'s `component` prop to the new approach
- update tests to avoid relying on `history`
- and more

While this does update us to React Router 6 there is still more to
be done to take advantage of the new features, such as the `handle`
prop on `Route`s to avoid the need for our custom `NamespacedRoute`
component etc. This will be tackled in the near future and will
dramatically simplify the code, allowing for a more uniform approach
to handling Kube resources without the current overhead of custom
containers per kind etc.
@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels May 17, 2024
Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 20, 2024
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 20, 2024
@tekton-robot tekton-robot merged commit 2572e8e into tektoncd:main May 20, 2024
8 checks passed
@AlanGreene AlanGreene deleted the react-router-6 branch May 20, 2024 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants